-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: k6runner: improve error handling for k6 output #1063
Conversation
41eaa1f
to
856e47e
Compare
856e47e
to
cb74f61
Compare
hello @roobre, thank you for your work! Do you have an estimate for when this might be merged? |
Hey @devtony15, I expect to finish testing this week, so hopefully it will be merged a few days later. As per Grafana policy we have stopped making releases due to the holiday season, so my expectation is for this to be released early January. |
@mem hey, could you review it please?) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Just added a couple of nit comments.
Closes #1060
This pull requests brings a number of improvements to how the local k6 runner, mostly used in private probe context, handles errors from k6. Most prominently:
nil, err
(understood as "k6 could not be run"), but rather a response with a textual representation of the error, and the k6 output. This still causes the test to be marked as failed, but the error is reported to Loki and thus made visible.Based on #1061 as I want CI/CD to be able to run.